DevOps & SysAdmins: fatal

The sftp login fails with the error fatal: bad ownership or modes for chroot directory in the secure log of the ssh server side.

可能导致的原因：错误的目录权限设定会导致在log中出现”fatal: bad ownership or modes for chroot directory XXXXXX” 的内容。

sshd[8707]: fatal: bad ownership or modes for chroot directory /home/sftpuser sshd[8636]: pam_unix(sshd:session): session closed for user.

Create your userid's per the indicated owners ( chown of the vhosts directories as required) and set the paths in the individual user profiles.

Code: sshd[20656]: fatal: bad ownership or modes for chroot directory /home/test. I am aware how to setup it using recommended config, lack ...

This is caused by permissions set on the chroot directory. The fix is to remove the SFTP user's write access to the chroot directory.

All components of the pathname must be root-owned directories that are not writable by any other user or group.

This is your error log: fatal: bad ownership or modes for chroot directory component / This means that you need to make sure to fulfil the emphasised part of ...

The issue was that every directory subcomponent should have write access only for root. In my case, / had write permissions for group. but /home and /home/xxx- ...

I'm trying to setup an sftp server and I want to be able to place the user in a specific unique directory, based on their username, without using /home.